Sprint Planning Oct 8

Doc TypeSprint Planning

Sprint Planning Meeting Minutes:

Project: Learnr

Attendees: Rose, Amani

Start time: 6:00 PM

End time: 7:00 PM

After discussion, the velocity of the team was estimated to be

The product owner chose the following user stories to be done during the next sprint. They are ordered based on their priority.

  1. User Story 16: As a developer, I want to transition the Learnr project from using a CSV database to a relational database, so that we can efficiently manage and access data.
  1. User Story 1 (Revisited): As a user, I want to be able to see my profile information - Now using the relational database
  1. User Story 2 (Revisited): As a user, I want to be able to fill up my account profile with additional information to my profile such as bio, interests, school, so that my profile is complete and reflects my identity within the system - Now using the relational database. Upon creation of a user, all profile information characteristics are filled in with null values (that show nothing if value is true, and get replaced with actual value if information if edited)
  1. User Story 3 (Revisited): As a user, I want the ability to edit my account profile information, so that I can keep it up to date as my details change - Now using the relational database
  1. User Story 4 (Revisited): As a super mentor, I want the ability to reset the password of other users, so that I can assist them in case they forget their password or encounter login issues. - Now using the relational database
  1. Stretch work:
    1. Revisit the previous User stories and adapt to the new database

The team members indicated their willingness to work on the following user stories.